home *** CD-ROM | disk | FTP | other *** search
- From: David Byrden <100101.2547@compuserve.com>
- Message-ID: <4dsr6m$tr5@news.bridge.net>
- X-Original-Date: 21 Jan 1996 07:49:42 GMT
- Path: in1.uu.net!bounce-back
- Date: 21 Jan 96 10:58:18 GMT
- Approved: fjh@cs.mu.oz.au
- Newsgroups: comp.std.c++
- Subject: Clarify DWP wording please
- Organization: self-employed
- X-Mailer: Mozilla 1.1N (Windows; I; 16bit)
- X-Auth: PGPMoose V1.1 PGP comp.std.c++
- iQBFAgUBMQIcXeEDnX0m9pzZAQHF4wF+NXimepyETajDfc7O/0Adtf5AtIMZuIbz
- qrBdeBA62Z9LppvsVuJA+dzQmwagiNtt
- =SAuq
-
- An earlier post of mine seems to be lost, so here is my question put in
- another light;
-
- The Sep 95 standard says, for certain containers, that in certain cases
- an operation will not invalidate iterators and references to its
- elements. For example, 23.2.5.6
-
- "If no reallocation happens, all the iterators and references before the
- insertion point remain valid."
-
- My question; by "references", does it mean actual T& that you may have
- declared like so;
-
- T& myRef = myVector[0] ;
-
- OR does it mean objects of the container's own specific reference type,
- like this;
-
- vector<int>::reference = myVector[0] ;
-
- This distinction is not trivial; it will determine allocators can be used
- with memory devices other than plain RAM.
-
-
- David
- ---
- [ comp.std.c++ is moderated. Submission address: std-c++@ncar.ucar.edu.
- Contact address: std-c++-request@ncar.ucar.edu. The moderation policy
- is summarized in http://dogbert.lbl.gov/~matt/std-c++/policy.html. ]
-